Benchmark EIE – Data Groups

Data Groups

With few exceptions, data groups must be defined in a device template file (DTF) in order for them to be available for use on a remote device. Which data groups are defined by a device template file depends on protocol, device type, and unique configuration.

CygNet distributes sample device template files for its EIEs, each of which typically serves one or more hardware models along with applicable firmware. Therefore, the data groups described below are only those data groups defined by CygNet in sample device template file(s). Your template(s) might not include some of the data groups described below. Device template files exist to enable users to customize device configurations; however, CygNet is not responsible for changes made by users.

For information about data group definitions and device template files, see Device Template Files.

For more information about data group dependencies, see Data Group Dependencies.

Notes:

In data groups in edit mode, a Send only edited items check box displays on the View Data dialog box, and when selected, only the edited values are written to the DDS transaction.
When point processing is performed on history data groups, only closed records will be published and processed to points. If a device has leading timestamped records and returns the current, open record, point processing will not be performed for that record, even though there is data in the DDS transaction. The point record will be updated only when that record is closed. This is to avoid a situation where a point has multiple entries with the same timestamp, since an open record may be still updating values with each new poll, but each update will have the same timestamp. For example, say you start polling for a daily history record at 8:00am, you’ll get the first value at 8:00am, then if you poll every five minutes, you’ll get new values throughout the day at the exact same timestamp. A history record is basically an array of data with a timestamp and values where the values have different process variables for each incremental poll. The timestamp won’t get written until the record is closed, which happens at the end of the time period, in this case, a day.

Benchmark EIE Data Groups

Browse by letter: [A] [C] [D] [E] [G] [H] [M] [P] [R] [S]

Data Group Type	Usage Notes
Audit	"Audit Trail" returns all history for all meters.
CfgMB	"Configurable Modbus"
CfgPt	"Configurable Points"
DateTime	"Date/Time"
DiagMsg	"Diagnostic Message"
EventRpt	"Event Report"
GmrCfgSend	"FMS Legacy Config Send Data" is used to send modified measurement data to the field device. This data group is required only if you plan to use FMS and want to perform this specific task. See FMS Legacy Config Send Data Group.
GmrConfig	"FMS Legacy Configuration Data" receives data from Meter Run Data. See FMS Legacy Configuration Data Group.
GmrEvent	"FMS Legacy Events Data" receives data from Audit Trail. Uses the previously retrieved transaction if the data range is sufficient. Specify date ranges on a per-data group basis within the device editor. For more information, see Selecting Date and Time. See FMS Legacy Events Data Group.
GmrHist	"FMS Legacy History Data" receives data from History Hourly data groups. Uses the previously retrieved transaction if the data range is sufficient. Specify date ranges on a per-data group basis within the device editor. For more information, see Selecting Date and Time. See FMS Legacy History Data Group.
HistDlyC	"History Daily Cone"
HistDlyL	"History Daily Liquid"
HistDlyO	"History Daily Orifice"
HistDlyT	"History Daily Turbine"
HistGq01	"History Gas Quality Src 1"
HistGq02	"History Gas Quality Src 2"
HistHlyC	"History Hourly Cone"
HistHlyL	"History Hourly Liquid"
HistHlyO	"History Hourly Orifice"
HistHlyT	"History Hourly Turbine"
HistPV	"History PV"
MeterRun	"Meter Run Data"
ModTest1	"MODBUS Sample 1"
ModTest2	"MODBUS Sample 2"
PointTbl01	"Table 01 - AI"
PointTbl02	"Table 02 - DI"
PointTbl03	"Table 03 - DO"
PointTbl04	"Table 04 - AO"
PointTbl13	"Table 13 - Supervisory"
PointTbl14	"Table 14 - AI(2)"
PointTbl15	"Table 15 - DI(2)"
PointTbl38	"Table 38 - Cone"
PointTbl39	"Table 39 - Energy Calculation"
PointTbl41	"Table 41 - Orifice"
PointTbl42	"Table 42 - Turbine"
PointTbl43	"Table 43 - Liquid"
PointTbl61	"Table 61"
PointTbl99	"Table 99 - System Events"
RtuConfig	"RTU Config" A valid RTU Config must be retrieved before other data groups can be retrieved or sent.
SingleMB	"Single Modbus Register"
SinglePt	"Single Point"